Lighttpd must produce log records containing sufficient information to establish the outcome (success or failure) of events.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-240224	VRAU-LI-000075	SV-240224r879567_rule		Medium

Description
Ascertaining the success or failure of an event is important during forensic analysis. Correctly determining the outcome will add information to the overall reconstruction of the logable event. By determining the success or failure of the event correctly, analysis of the enterprise can be undertaken to determine if events tied to the event occurred in other areas within the enterprise. Without sufficient information establishing the success or failure of the logged event, investigation into the cause of event is severely hindered. The success or failure also provides a means to measure the impact of an event and help authorized personnel to determine the appropriate response. Log record content that may be necessary to satisfy the requirement of this control includes, but is not limited to, time stamps, source and destination IP addresses, user/process identifiers, event descriptions, application-specific events, success/fail indications, file names involved, access control, or flow control rules invoked. Lighttpd logs user activity in the access.log file using the Common Log Format (CLF). The CLF format, a World Wide Web Consortium standard, captures logs all user session information related to the hosted application session. This will enable forensic analysis of server events in case of malicious event.

Description

Ascertaining the success or failure of an event is important during forensic analysis. Correctly determining the outcome will add information to the overall reconstruction of the logable event. By determining the success or failure of the event correctly, analysis of the enterprise can be undertaken to determine if events tied to the event occurred in other areas within the enterprise. Without sufficient information establishing the success or failure of the logged event, investigation into the cause of event is severely hindered. The success or failure also provides a means to measure the impact of an event and help authorized personnel to determine the appropriate response. Log record content that may be necessary to satisfy the requirement of this control includes, but is not limited to, time stamps, source and destination IP addresses, user/process identifiers, event descriptions, application-specific events, success/fail indications, file names involved, access control, or flow control rules invoked. Lighttpd logs user activity in the access.log file using the Common Log Format (CLF). The CLF format, a World Wide Web Consortium standard, captures logs all user session information related to the hosted application session. This will enable forensic analysis of server events in case of malicious event.

STIG	Date
VMware vRealize Automation 7.x Lighttpd Security Technical Implementation Guide	2023-09-12

Details

Check Text ( C-43457r668003_chk )
At the command prompt, execute the following command: Note: The HTTP status code indicating success or failure is a 3-digit integer immediately after "HTTP/1.1". Any value other than a 3-digit code immediately following "HTTP/1.1" is a failure of the logging process. tail -n 4 /opt/vmware/var/log/lighttpd/access.log If any of the generated audit records are without sufficient information to establish the outcome of the event (success or failure), this is a finding.

Check Text ( C-43457r668003_chk )

At the command prompt, execute the following command:

Note: The HTTP status code indicating success or failure is a 3-digit integer immediately after "HTTP/1.1". Any value other than a 3-digit code immediately following "HTTP/1.1" is a failure of the logging process.

tail -n 4 /opt/vmware/var/log/lighttpd/access.log

If any of the generated audit records are without sufficient information to establish the outcome of the event (success or failure), this is a finding.

Fix Text (F-43416r667848_fix)
Navigate to and open the /opt/vmware/etc/lighttpd/lighttpd.conf file Configure the "lighttpd.conf" file with the following: $HTTP["url"] !~ "(.css\|.jpg\|.gif\|.png\|.ico)$" { accesslog.filename = log_root + "/access.log" }